X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C93551.3D21605A@onstor-exch02.onstor.net>; Thu, 23 Oct 2008 13:52:19 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93551.3D21605A"
Content-class: urn:content-classes:message
Subject: RE: Lun Label type-5 Functional Spec. for Kegg
Date: Thu, 23 Oct 2008 13:52:18 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0C19C9C2@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0C19C93A@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Lun Label type-5 Functional Spec. for Kegg
Thread-Index: Ack0pDOGwsjJ1gNkTEyXhNf4IHF7KQAiul2wAAEHxdAAAFt/oAAAU/bAAAMjlBA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E038F913D@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E038F913E@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0C19C93A@onstor-exch02.onstor.net>
From: "Deepak Veliath" <deepak.veliath@onstor.com>
To: "dl-Design Review" <dl-designreview@onstor.com>,
	"dl-Kegg" <dl-Kegg@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93551.3D21605A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Jim,
*	From reading the spec I understand you are making space appended
to a physical LUN accessible by exporting them as partitions or as you
call them, LUN extents.  What would the device IDs for these partitions
be as displayed by "lun show disk"?
*	From the Figure 10 it would seem there is only a single owner
block for the whole physical LUN.  Does this mean that only a single
node in a cluster can access the partitions at any given time.
*	If a partition has no FS on it, does it make to append space
added to the physical LUN to be added directly to the partition?
*	Regd Solaris disk-labels, AFAIK on an Intel based system Solaris
creates a PC MBR, allocates the whole disk (skipping the 1st track) to a
primary partition of type 0x82 and slices that partition up using its
native partitioning logic which I believe is very similar to the BSDs.
So I believe we're safe on x86 systems running Solaris (which in turn
means Leopards can co-exist with Cougars on the SAN?).

Do let me know.

Thank you,
veliath


------_=_NextPart_001_01C93551.3D21605A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: Lun Label type-5 Functional Spec. for Kegg</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Verdana">Hello Jim,</FONT>

<UL>
<LI><FONT SIZE=3D2 FACE=3D"Verdana">From reading the spec I understand =
you are making space appended to a physical LUN accessible by exporting =
them as partitions or as you call them, LUN extents.&nbsp; What would =
the device IDs for these partitions be as displayed by &quot;lun show =
disk&quot;?</FONT></LI>

<LI><FONT SIZE=3D2 FACE=3D"Verdana">From the Figure 10 it would seem =
there is only a single owner block for the whole physical LUN.&nbsp; =
Does this mean that only a single node in a cluster can access the =
partitions at any given time.</FONT></LI>

<LI><FONT SIZE=3D2 FACE=3D"Verdana">If a partition has no FS on it, does =
it make to append space added to the physical LUN to be added directly =
to the partition?</FONT></LI>

<LI><FONT SIZE=3D2 FACE=3D"Verdana">Regd Solaris disk-labels, AFAIK on =
an Intel based system Solaris creates a PC MBR, allocates the whole disk =
(skipping the 1st track) to a primary partition of type 0x82 and slices =
that partition up using its native partitioning logic which I believe is =
very similar to the BSDs.&nbsp; So I believe we're safe on x86 systems =
running Solaris (which in turn means Leopards can co-exist with Cougars =
on the SAN?).</FONT></LI>
<BR>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Verdana">Do let me know.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Verdana">Thank you,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Verdana">veliath</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C93551.3D21605A--
